SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Hardware architecture</title>

</head>

Hardware architecture

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">This article is about Hardware Architecture; the term refers to the architectural design of a physical device, or system, often comprising both hardware and software. For other uses, see for example <a href="Computer_architecture" title="Computer architecture">Computer architecture</a>, <a href="Computer_hardware" title="Computer hardware">Computer hardware</a> or <a href="Architecture_(disambiguation)" class="mw-disambig" title="Architecture (disambiguation)">Architecture (disambiguation)</a>.</div>

In engineering, hardware architecture refers to the identification of a system's physical components and their interrelationships. This description, often called a hardware design model, allows hardware designers to understand how their components fit into a system architecture and provides to software component designers important information needed for software development and integration. Clear definition of a hardware architecture allows the various traditional engineering disciplines (e.g., electrical and mechanical engineering) to work more effectively together to develop and manufacture new machines, devices and components.<a href="#cite_note-1">[1]</a>

Hardware is also an expression used within the computer engineering industry to explicitly distinguish the (<a href="Electronic_computer" class="mw-redirect" title="Electronic computer">electronic computer</a>) hardware from the software that runs on it. But hardware, within the <a href="Automation" title="Automation">automation</a> and <a href="Software_engineering" title="Software engineering">software engineering</a> disciplines, need not simply be a computer of some sort. A modern automobile runs vastly more software than the Apollo spacecraft. Also, modern aircraft cannot function without running tens of millions of computer instructions embedded and distributed throughout the aircraft and resident in both standard computer hardware and in specialized hardware components such as IC wired logic gates, analog and hybrid devices, and other digital components. The need to effectively model how separate physical components combine to form complex systems is important over a wide range of applications, including computers, personal digital assistants (PDAs), cell phones, surgical instrumentation, satellites, and submarines.

Hardware architecture is the representation of an engineered (or to be engineered) electronic or electromechanical hardware system, and the process and discipline for effectively implementing the <a href="Design" title="Design">design</a>(s) for such a system. It is generally part of a larger integrated system encompassing <a href="Information" title="Information">information</a>, <a href="Software" title="Software">software</a>, and device <a href="Prototyping" class="mw-redirect" title="Prototyping">prototyping</a>.<a href="#cite_note-2">[2]</a>

It is a representation because it is used to convey information about the related <a href="https://en.wiktionary.org/wiki/element" class="extiw external" title="wiktionary:element">elements</a> comprising a hardware system, the relationships among those elements, and the <a href="https://en.wiktionary.org/wiki/rule" class="extiw external" title="wiktionary:rule">rules</a> governing those relationships.

It is a process because a sequence of steps is prescribed to produce or change the architecture, and/or a design from that architecture, of a hardware system within a set of constraints.

It is a discipline because a body of knowledge is used to inform practitioners as to the most effective way to design the system within a set of constraints.

A hardware architecture is primarily concerned with the internal electrical (and, more rarely, the <a href="Electromechanics" title="Electromechanics">mechanical</a>) <a href="Electrical_connector" title="Electrical connector">interfaces</a> among the system's <a href="Software_componentry" class="mw-redirect" title="Software componentry">components</a> or <a href="System" title="System">subsystems</a>, and the <a href="Computer_bus" class="mw-redirect" title="Computer bus">interface</a> between the system and its external environment, especially the devices operated by or the electronic displays viewed by a <a href="User_(computing)" title="User (computing)">user</a>. (This latter, special interface, is known as the <a href="Computer_human_interface" class="mw-redirect" title="Computer human interface">computer human interface</a>, AKA human computer interface, or <a href="Human-computer_interaction" class="mw-redirect" title="Human-computer interaction">HCI</a>; formerly called the man-machine interface.)<a href="#cite_note-3">[3]</a> Integrated circuit (IC) designers are driving current technologies into innovative approaches for new products. Hence, multiple layers of active devices are being proposed as single chip, opening up opportunities for disruptive microelectronic, optoelectronic, and new microelectromechanical hardware implementation.<a href="#cite_note-4">[4]</a><a href="#cite_note-5">[5]</a>

<div class="mw-heading mw-heading2"><h2 id="Background">Background</h2></div>

Prior to the advent of digital computers, the electronics and other engineering disciplines used the terms system and hardware as they are still commonly used today. However, with the arrival of digital computers on the scene and the development of software engineering as a separate discipline, it was often necessary to distinguish among engineered hardware artifacts, software artifacts, and the combined artifacts.

A <a href="Computer_program" title="Computer program">programmable</a> hardware artifact, or machine, that lacks its computer program is impotent; even as a software artifact, or program, is equally impotent unless it can be used to alter the sequential states of a suitable (hardware) machine. However, a hardware machine and its programming can be designed to perform an almost illimitable number of abstract and physical tasks. Within the computer and software engineering disciplines (and, often, other engineering disciplines, such as communications), then, the terms hardware, software, and system came to distinguish between the hardware that runs a <a href="Computer_program" title="Computer program">computer program</a>, the software, and the hardware device complete with its program.

A hardware can be controlled from a software with the help of a middle device called hardware controller, this hardware controller can be used to perform various automated task from hardware, generally hardware controller consist of GPIO(general purpose input and output) pins, these pin's behaviour controlled by the piece of code.<a href="#cite_note-6">[6]</a>

The hardware engineer or architect deals (more or less) exclusively with the hardware device; the software engineer or architect deals (more or less) exclusively with the program; and the systems engineer or <a href="Systems_architect" title="Systems architect">systems architect</a> is responsible for seeing that the programming is capable of properly running within the hardware device, and that the system composed of the two entities is capable of properly interacting with its external environment, especially the user, and performing its intended function.

A hardware architecture, then, is an abstract representation of an electronic or an electromechanical device capable of running a fixed or changeable program.<a href="#cite_note-7">[7]</a><a href="#cite_note-8">[8]</a>

A hardware architecture generally includes some form of analog, digital, or <a href="Hybrid_computer" title="Hybrid computer">hybrid electronic computer</a>, along with electronic and mechanical sensors and actuators. Hardware design may be viewed as a 'partitioning <a href="Scheme_(mathematics)" title="Scheme (mathematics)">scheme</a>,' or <a href="Algorithm" title="Algorithm">algorithm</a>, which considers all of the system's present and foreseeable requirements and arranges the necessary hardware components into a workable set of cleanly <a href="https://en.wiktionary.org/wiki/bounded" class="extiw external" title="wikt:bounded">bounded</a> <a href="Subsystem" class="mw-redirect" title="Subsystem">subsystems</a> with no more parts than are required. That is, it is a partitioning scheme that is exclusive, inclusive, and <a href="Collectively_exhaustive_events" title="Collectively exhaustive events">exhaustive</a>. A major purpose of the partitioning is to arrange the elements in the hardware subsystems so that there is a minimum of electrical connections and electronic communications needed among them. In both software and hardware, a good subsystem tends to be seen as a meaningful "<a href="Object_(computer_science)" title="Object (computer science)">object</a>." Moreover, a clear allocation of user requirements to the architecture (hardware and software) provides an effective basis for <a href="Verification_and_Validation" class="mw-redirect" title="Verification and Validation">validation tests</a> of the user's requirements in the as-built system.

<ul><li><a href="Computer-aided_manufacturing" title="Computer-aided manufacturing">Computer-aided manufacturing</a> (CAM)</li>

<li><a href="Electronic_design_automation" title="Electronic design automation">Electronic design automation</a> (EDA)</li>

<li><a href="Elmer_FEM_solver" title="Elmer FEM solver">Elmer FEM solver</a></li>

<li><a href="Finite_element_analysis" class="mw-redirect" title="Finite element analysis">Finite element analysis</a></li>

<li><a href="Hardware_architect" title="Hardware architect">Hardware architect</a></li>

<li><a href="Integrated_circuit" title="Integrated circuit">Integrated circuit</a> (IC)</li>

<li><a href="System-on-a-chip" class="mw-redirect" title="System-on-a-chip">System-on-a-chip</a> (SoC)</li>

<li><a href="Very-large-scale_integration" title="Very-large-scale integration">Very-large-scale integration</a> (VLSI)</li>

<li><a href="VHSIC_Hardware_Description_Language" class="mw-redirect" title="VHSIC Hardware Description Language">VHSIC Hardware Description Language</a> (VHDL)</li>

<li><a href="Technology_CAD" title="Technology CAD">Technology CAD</a> (TCAD)</li>

<li><a href="Open_Cascade_Technology" title="Open Cascade Technology">Open Cascade Technology</a></li>

<li><a href="Open_source_hardware" class="mw-redirect" title="Open source hardware">Open source hardware</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width reflist-columns-2">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFRai,_L.Kang,_S.J.2008" class="citation journal cs1">Rai, L.; Kang, S.J. (2008). "Rule-based modular software and hardware architecture for multi-shaped robots using real-time dynamic behavior identification and selection". Knowledge-Based Systems. 21 (4): 273–283. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.knosys.2007.05.008">10.1016/j.knosys.2007.05.008</a>.</cite>

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <cite id="CITEREFFrampton,_K.D.,_Martin,_S.E._&_Minor,_K.2003" class="citation journal cs1">Frampton, K.D., Martin, S.E. & Minor, K. (2003). "The scaling of acoustic streaming for application in micro-fluidic devices". Applied Acoustics. 64 (7): 681–692. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2FS0003-682X%2803%2900005-7">10.1016/S0003-682X(03)00005-7</a>.</cite><code class="cs1-code">{{cite journal}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite id="CITEREFBrunelli,_C.,_Garzia,_F._&_Nurmi,_J.2008" class="citation journal cs1">Brunelli, C., Garzia, F. & Nurmi, J. (2008). "A coarse-grain reconfigurable architecture for multimedia applications featuring subword computation capabilities". Journal of Real-Time Image Processing. 3 (1–2): 21–32. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs11554-008-0071-3">10.1007/s11554-008-0071-3</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:25962199">25962199</a>.</cite><code class="cs1-code">{{cite journal}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite id="CITEREFCale,_T.S.,_Lu,_J.-Q._&_Gutmann,_R.J.2008" class="citation journal cs1">Cale, T.S., Lu, J.-Q. & Gutmann, R.J. (2008). "Three-dimensional integration in microelectronics: Motivation, processing, and thermomechanical modeling". Chemical Engineering Communications. 195 (8): 847–888. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1080%2F00986440801930302">10.1080/00986440801930302</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:95022083">95022083</a>.</cite><code class="cs1-code">{{cite journal}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite id="CITEREFCavalcanti,_A.,_Shirinzadeh,_B.,_Zhang,_M._&_Kretly,_L.C.2008" class="citation journal cs1">Cavalcanti, A., Shirinzadeh, B., Zhang, M. & Kretly, L.C. (2008). <a rel="nofollow" class="external text" href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3675524">"Nanorobot Hardware Architecture for Medical Defense"</a>. Sensors. 8 (5): 2932–2958. <a href="Bibcode_(identifier)" class="mw-redirect" title="Bibcode (identifier)">Bibcode</a>:<a rel="nofollow" class="external text" href="https://ui.adsabs.harvard.edu/abs/2008Senso...8.2932C">2008Senso...8.2932C</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.3390%2Fs8052932">10.3390/s8052932</a>. <a href="PMC_(identifier)" class="mw-redirect" title="PMC (identifier)">PMC</a> <a rel="nofollow" class="external text" href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3675524">3675524</a>. <a href="PMID_(identifier)" class="mw-redirect" title="PMID (identifier)">PMID</a> <a rel="nofollow" class="external text" href="https://pubmed.ncbi.nlm.nih.gov/27879858">27879858</a>.</cite><code class="cs1-code">{{cite journal}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://techsoverflow.com/">"Techsoverflow - it is all about tech Techsoverflow"</a>. Retrieved 2022-12-17.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite id="CITEREFAssif,_D.,_Himel,_R._&_Grajower,_Y.1988" class="citation journal cs1">Assif, D., Himel, R. & Grajower, Y. (1988). "A new electromechanical device to measure the accuracy of interocclusal records". Journal of Prosthetic Dentistry. 59 (6): 672–676. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2F0022-3913%2888%2990380-0">10.1016/0022-3913(88)90380-0</a>. <a href="PMID_(identifier)" class="mw-redirect" title="PMID (identifier)">PMID</a> <a rel="nofollow" class="external text" href="https://pubmed.ncbi.nlm.nih.gov/3165452">3165452</a>.</cite><code class="cs1-code">{{cite journal}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> <cite id="CITEREFZimmermann,_M.,_Volden,_T.,_Kirstein,_K.-U.,_Hafizovic,_S.,_Lichtenberg,_J.,_Brand,_O._&_Hierlemann,_A.2008" class="citation journal cs1">Zimmermann, M., Volden, T., Kirstein, K.-U., Hafizovic, S., Lichtenberg, J., Brand, O. & Hierlemann, A. (2008). "A CMOS-based integrated-system architecture for a static cantilever array". Sensors and Actuators B: Chemical. 131 (1): 254–264. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.snb.2007.11.016">10.1016/j.snb.2007.11.016</a>.</cite><code class="cs1-code">{{cite journal}}</code>: CS1 maint: multiple names: authors list (link)

</li>

</ol></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-01-05" href="https://en.wikipedia.org/wiki/?title=Hardware_architecture&oldid=1267510803">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>